Repository navigation
Run the before-publish build only in the publish run - #244
Merged
Merged
Conversation
The step had no condition, so it ran on pull_request, merge_group, and the main run that commits the version bump. A block passes build:release here, and block-tools software build uploads binaries in that build. A PR run with a changeset version uploads the binaries of a version that is not released yet. When the PR changes its bump, that version stays in the registry. The later release finds the file, skips the upload with a warning, and ships the old binaries. clonotype-clustering: PR #156 run 39406490270 uploaded software 4.3.0 from 4.2.1 code. Release 4.3.0 (PR #163) skipped the upload and shipped those files. Use the condition of the npm pack step: main, with no version-bump changes left.
|
Automatic reviews are disabled for this repository. Configure in Code Review Settings. |
Contributor
Author
How the
|
DenKoren
approved these changes
Nov 11, 2026
DenKoren
left a comment
Member
There was a problem hiding this comment.
Check this scenario, please, if not yet:
- build happens in worker 1. It creates package but does not upload it.
- turbo cache uploads cached files into remote storage
- the next step (publish) gets cache hit, puts files from cache to disk and skips the build process: no package archives are on disk and nothing to upload.
- publish step tries to ensure packages are on remote side, they are not and there is no local archive to upload == failure.
On the ubuntu-26.04 runner image 20261101, apt cannot resolve the Ubuntu archive hosts, and the Install bats step fails. The npm registry resolves on the same runner. The npm package has the same version, 1.13.0, that apt installed on image 20261025.
This was referenced Nov 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Run build (before publish)innode-simple-pnpm.yamlhas no condition. It runs onpull_request,merge_group, and the main run that commits the version bump. A block passesbuild-before-publish-script-name: build:release, which is the default of the block-tools template since platforma83298ed6a7. Since MILAB-6497,block-tools software builduploads the binaries in that build whenPL_BUILD_LOCATION=remote. Before that, the upload ran inprepublishOnly, only atnpm publish.PR runs also apply
changeset version, so a PR run uploads the binaries of the next release version. When the PR changes its bump or closes, that version stays in the registry. The release that later gets the version finds the file.package-builder-libcore.tslogsalready exists … Upload was skipped, and the step stays green. The release then ships the old binaries.Incident: clonotype-clustering 4.3.0
software: minor. The run computed 4.2.1 → 4.3.0 and uploaded…/4.3.0.tgzwith the 4.2.x scripts. The PR then switched topatchand released 4.2.2.software: minorgave 4.2.3 → 4.3.0. Turbo cache miss: the build ran, and all four uploads were skipped asalready exists.d25cdc827d826de1), and the release shipped descriptors for the old files.The
process-results/4.3.0.tgzonbin.pl-open.sciencehas file dates of Oct 20 12:44 CEST, and its content is identical to 4.2.3. clonotype-clustering#164 worked around it with 4.3.1.Change
The step now uses the condition of
Pack unpublished npm packages:Run build(build-script-name)Run build (before publish)pull_requestmerge_group(gh-readonly-queue/…)pushmain, version bump pending (has-changes == '1')pushmain, nothing to bump (has-changes == '0')Tradeoff
PR runs no longer run the release-channel build. A failure that only
build:releaseshows appears first on main.build-script-name(build:dev-localfor blocks) still builds the whole workspace on every PR.Not in this PR
block-toolsrun-build.tsdoes not passfailExistingfor the release channel, so a taken slot is a warning and not an error.Check
actionlintreports no new findings: the same 20 findings asv4, all from earlier code.